Adds a VLAN or VMAN service to a VPLS or VPWS.
| vpls_name | Identifies the VPLS interface within the switch (character string). |
| vpws_name | Identifies the VPWS interface within the switch (character string). |
| vlan_name | Logically binds the VLAN to the specified VPLS or VPWS. |
| vman_name | Adds the named VMAN to the VPLS or VPWS. |
N/A.
Only one VLAN or VMAN can be configured per VPLS or VPWS.
When a VLAN service is added to a VPLS or VPWS, the VLAN ID is locally significant to the switch. Thus, each VLAN VPLS or VPWS interface within the Layer 2 VPN can have a different VLAN ID. This greatly simplifies VLAN ID coordination between metro network access points. Traffic may be switched locally between VLAN ports if more than one port is configured for the VLAN.
When a VMAN service has been configured for a VPLS or VPWS, the VMAN ID is locally significant to the switch. Thus, each VMAN VPLS or VPWS interface within the Layer 2 VPN can have a different VMAN ID, just like the VLAN service. The only difference is that the Layer 2 VPN overwrites the outer VMAN tag on Layer 2 VPN egress and leaves the inner VLAN tag unmodified. Because the inner VLAN tag is considered part of the customer packet data, the VMAN service can be used to emulate port-based services. This is accomplished by configuring the Layer 2 VPN to strip the 802.1Q tag from the tunneled packet. Since the switch inserts the VMAN tag when the packet is received and the 802.1Q tag is stripped before the packet is sent on the VPLS or VPWS PW, all packets received on ports that are members of the VMAN are transmitted unmodified across the Layer 2 VPN. The command configure l2vpn [vpls vpls_name | vpws vpws_name] dot1q tag exclude is used to configure the switch to strip the 802.1Q tag on the VPLS.
The l2vpn keyword was introduced in ExtremeXOS Release 12.4 and is required when adding a service to VPWS. For backward compatibility, the l2vpn keyword is optional when adding a service to VPLS. However, this keyword will be required in a future release, so we recommend that you use this keyword for new configurations and scripts.
The example below adds a VLAN and a VMAN to the named VPLS:
configure l2vpn vpls myvpls add service vlan myvlan configure l2vpn vpls myvpls add service vman myvman
The following example adds a VLAN and a VMAN to the named VPWS:
configure l2vpn vpws myvpws add service vlan vlan2
configure l2vpn vpws myvpws add service vman vman2
This command was first available in ExtremeXOS 11.6.
The l2vpn and vpws keywords were first available in ExtremeXOS 12.4.
This command is available only on the platforms that support MPLS as described in the Switch Engine v33.1.1 Licensing Guide document.